Skip to contentSkip to conversation

ipv4_reassembly: start examples/dpdk-ip_reassembly fail

DPDK/examples Bug 1785 [email protected] 1 participant 1 message Sep 10, 2025

lore
Share & tools
lore
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=1785

            Bug ID: 1785
           Summary: [dpdk-25.11.0-rc0]ipv4_reassembly: start
                    examples/dpdk-ip_reassembly fail
           Product: DPDK
           Version: 25.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: examples
          Assignee: [email protected]
          Reporter: [email protected]

Target Milestone: ---

Environment
===========
DPDK version: 9fe9c0b231c8da5435bfccb1963121b4277f961c version: dpdk25.07-rc3
OS: Fedora42/6.14.5-300.fc42.x86_64
Compiler: gcc version 15.2.1 20250808
Hardware platform: Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz
NIC hardware: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev
01)
NIC firmware:
driver: vfio-pci
kdriver: i40e-2.28.7
firmware-version: 9.54 0x8000fb3f 1.3800.0

Test Setup
Steps to reproduce
==================
1.Build dpdk and examples=ip_reassembly
CC=gcc meson -Denable_kmods=False -Dlibdir=lib -Dexamples=ip_reassembly --default-library=static x86_64-native-linuxapp-gcc -Dmax_lcores=160 ninja -C x86_64-native-linuxapp-gcc

2.Start dpdk-ip_reassembly
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:31:00.0 0000:31:00.1 ./x86_64-native-linuxapp-gcc/examples/dpdk-ip_reassembly -l 1 -n 4 -a 0000:31:00.0 -a 0000:31:00.1 --file-prefix=dpdk_513316_20250910130931
--force-max-simd-bitwidth=64 -- -p 0x1 --maxflows=1024 --flowttl=3s

Results:
========
EAL: Detected CPU lcores: 160
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/dpdk_513316_20250910130931/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
IP_RSMBL: Creating LPM table on socket 0
IP_RSMBL: Creating LPM6 table on socket 0
IPFRAG: rte_ip_frag_table_create: allocated of 8388736 bytes at socket 0 Initializing port 0 ... Port 0 modified RSS hash function based on hardware support,requested:0xa38c configured:0x228c
ETHDEV: id=0 offload clash, MULTI_SEGS vs MBUF_FAST_FREE

EAL: Error - exiting with code: 1
Cannot configure device: err=-22, port=0

Expected Result:
================
EAL: Detected CPU lcores: 160
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/dpdk_513316_20250910130931/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
I40E_DRIVER: i40e_GLQF_reg_init(): i40e device 0000:31:00.0 changed global register [0x002689a0]. original: 0x00000021, new: 0x00000029
IP_RSMBL: Creating LPM table on socket 0
IP_RSMBL: Creating LPM6 table on socket 0
IPFRAG: rte_ip_frag_table_create: allocated of 8388736 bytes at socket 0 Initializing port 0 ... Port 0 modified RSS hash function based on hardware support,requested:0xa38c configured:0x228c
Address:3C:FD:FE:C0:E1:D8
txq=1,0,0

Skipping disabled port 1
......
Checking link status
done
Port 0 Link up at 25 Gbps FDX Autoneg
IP_RSMBL: entering main loop on lcore 1
IP_RSMBL: -- lcoreid=1 portid=0

bad commit:
===========
commit fdb840367cf0d6abeb17b05623679b8d1ea4c902

Author: Morten Brørup <[email protected]>
Date:   Sun Aug 3 19:42:18 2025 +0000

ethdev: reject conflicting Tx offload configurations

When an ethdev port is configured for fast mbuf release, the driver can use a Tx burst function relying on the fast mbuf release preconditions. Thus, also configuring this port or a queue on the port for transmitting segmented packets is prohibited.
Checks for these conflicting configurations have been added to the ethdev library, so the drivers don't have to implement them.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.